[WIP] New Installing MTA UI and CLI title #173

mpershina · 2025-08-01T10:45:22Z

Tracked under MTA-4209.
Gdoc draft

Preview: https://mpershina.github.io/Previews/MTA/install-guide.html

docs/topics/mta-install/proc_installing-mta-operator.adoc

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

anarnold97 · 2025-08-12T13:00:25Z

docs/install-guide/master-docinfo.xml

did you mean to include this file?

anarnold97 · 2025-08-12T13:11:16Z

docs/topics/mta-install/con_mta-tools.adoc

+
+
+
+You can use these add-on to perform the following tasks: 


Suggested change

You can use these add-on to perform the following tasks:

You can use these add-ons to perform the following tasks:

use plural and singular nouns correctly

anarnold97 · 2025-08-12T13:11:28Z

docs/topics/mta-install/con_mta-tools.adoc

+
+
+
+You can use these add-on to perform the following tasks: 


Suggested change

You can use these add-on to perform the following tasks:

You can use this add-on to perform the following tasks:

anarnold97 · 2025-08-12T13:15:02Z

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

+[id="roles-personas-users-permissions_{context}"]
+= Roles, personas, users, and permissions
+
+The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona: 


Suggested change

The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona:

The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona:

anarnold97 · 2025-08-12T13:16:56Z

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

+
+The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona: 
+
+* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files.


Suggested change

* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files.

* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume but cannot change or view, for example, Git credentials or Maven `settings.xml` files.

anarnold97 · 2025-08-12T13:17:23Z

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

+
+* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files.
+
+* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application. 	


Suggested change

* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application.

* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information but can consume it. For example, the architect can associate an existing credential to the repository of a specific application.

anarnold97 · 2025-08-12T13:20:04Z

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

+
+* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application. 	
+
+* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them. 


Suggested change

* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them.

* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications but not create, modify, or delete them.

anarnold97 · 2025-08-12T13:21:25Z

docs/topics/mta-install/con_roles-personas-users-permissions.adoc

+
+* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them. 
+
+{ProductShortName} has two views, *Administration* and *Migration*. Only administrators can access the *Administration* view. Architects and migrators have no access to Administration view, they cannot even see it. Administrators can perform all actions supported by *Migration* view. Architects and migrators can see all elements of *Migration* view, but their ability to perform actions in *Migration* view depends on the permissions granted to their role.


Suggested change

{ProductShortName} has two views, *Administration* and *Migration*. Only administrators can access the *Administration* view. Architects and migrators have no access to Administration view, they cannot even see it. Administrators can perform all actions supported by *Migration* view. Architects and migrators can see all elements of *Migration* view, but their ability to perform actions in *Migration* view depends on the permissions granted to their role.

{ProductShortName} has two views, *Administration* and *Migration*. Only administrators can access the *Administration* view. Architects and migrators have no access to Administration view, they cannot even see it. Administrators can perform all actions supported by *Migration* view. Architects and migrators can see all elements of *Migration* view but their ability to perform actions in *Migration* view depends on the permissions granted to their role.

anarnold97 · 2025-08-12T13:30:47Z

docs/topics/mta-install/proc_creating-mta-instance.adoc

+[id="creating-mta-instance_{context}"]
+= Creating a MTA instance
+
+You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process, at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift. 			


Suggested change

You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process, at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift.

You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift.

anarnold97

Some small nits but otherwise LGTM

anarnold97 · 2025-08-13T13:52:40Z

docs/topics/mta-install/proc_installing-cli-zip.adoc

this is not correct

[id="installing-downloadable-cli-zip_{context}"] == Installing the {CLINameTitle} `.zip` file .Procedure . Navigate to the link:{DevDownloadPageURL}[{ProductShortName} Download page] and download the OS-specific CLI file or the `src` file: + * {ProductShortNameLower}-{ProductVersion}-cli-linux-amd64.zip * {ProductShortNameLower}-{ProductVersion}-cli-linux-arm64.zip * {ProductShortNameLower}-{ProductVersion}-cli-darwin-amd64.zip * {ProductShortNameLower}-{ProductVersion}-cli-darwin-arm64.zip * {ProductShortNameLower}-{ProductVersion}-cli-windows-amd64.zip * {ProductShortNameLower}-{ProductVersion}-cli-windows-arm64.zip * {ProductShortNameLower}-{ProductVersion}-cli-src.zip . Extract the `.zip` file to the `.kantra` directory inside your `$HOME` directory. The `.zip` file extracts the *mta-cli* binary, along with other required directories and files.

Also, please note Igor's comments on this PR - https://github.com/migtools/mta-documentation/pull/178/files#r2273545164

FYI - @ibragins

New Install guide draft

ff95d18

mpershina commented Aug 1, 2025

View reviewed changes

docs/topics/mta-install/proc_installing-mta-operator.adoc Outdated Show resolved Hide resolved

mpershina commented Aug 1, 2025

View reviewed changes

docs/topics/mta-install/con_roles-personas-users-permissions.adoc Outdated Show resolved Hide resolved

Apply suggestions from code review

3351b4e

anarnold97 reviewed Aug 12, 2025

View reviewed changes

docs/install-guide/master-docinfo.xml

Copy link

Collaborator

anarnold97 Aug 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you mean to include this file?

anarnold97 reviewed Aug 12, 2025

View reviewed changes

This comment was marked as outdated.

Sign in to view

anarnold97 requested changes Aug 12, 2025

View reviewed changes

anarnold97 requested a review from ibragins August 13, 2025 13:51

anarnold97 reviewed Aug 13, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[WIP] New Installing MTA UI and CLI title #173

[WIP] New Installing MTA UI and CLI title #173

Uh oh!

mpershina commented Aug 1, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

anarnold97 Aug 12, 2025

Uh oh!

This comment was marked as outdated.

Uh oh!

anarnold97 left a comment

Uh oh!

anarnold97 Aug 13, 2025 •

edited

Loading

Uh oh!

Uh oh!

	You can use these add-on to perform the following tasks:
	You can use these add-ons to perform the following tasks:

	You can use these add-on to perform the following tasks:
	You can use this add-on to perform the following tasks:

	The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona:
	The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona:


		The {ProductFullName} uses three roles, each corresponds to a persona. The roles are already defined in your RHBK instance. You do not need to create them. If you are an {ProductShortName} administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona. Although a user can have more than one role, each role corresponds to a specific persona:

		* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files.


		* The `tackle-admin` role corresponds to the Administrator persona. The administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume, but cannot change or view, for example, Git credentials or Maven `settings.xml` files.

		* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application.


		* The `tackle-architect` role corresponds to the Architect persona. An architect is a technical lead for the migration project who can run assessments and can create and modify applications and information related to them. The architect cannot modify or delete sensitive information, but can consume it. For example, the architect can associate an existing credential to the repository of a specific application.

		* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them.


		* The `tackle-migrator` role corresponds to the Migrator persona. A migrator is a user who can analyze applications, but not create, modify, or delete them.

		{ProductShortName} has two views, Administration and Migration. Only administrators can access the Administration view. Architects and migrators have no access to Administration view, they cannot even see it. Administrators can perform all actions supported by Migration view. Architects and migrators can see all elements of Migration view, but their ability to perform actions in Migration view depends on the permissions granted to their role.

	You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process, at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift.
	You can use the {ProductFullName} user interface (UI) to assess and analyze your applications to get insights about the adoption process at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to Red Hat OpenShift.

[WIP] New Installing MTA UI and CLI title #173

Are you sure you want to change the base?

[WIP] New Installing MTA UI and CLI title #173

Uh oh!

Conversation

mpershina commented Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

Uh oh!

anarnold97 left a comment

Choose a reason for hiding this comment

Uh oh!

anarnold97 Aug 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mpershina commented Aug 1, 2025 •

edited

Loading

anarnold97 Aug 13, 2025 •

edited

Loading